Skip to content

Make OptableConfig options settable after construction - #64

Open
jrosendahl-opt wants to merge 1 commit into
masterfrom
feat/config-settable-from-java
Open

jrosendahl-opt wants to merge 1 commit into
masterfrom
feat/config-settable-from-java

Conversation

@jrosendahl-opt

@jrosendahl-opt jrosendahl-opt commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Why

host, path, insecure, apiKey, customUserAgent and cacheTtl were internal vals, so from Java the only way to set one was the @JvmOverloads constructor with every preceding parameter (eleven arguments to change cacheTtl). The iOS SDK exposes all of its config settings as vars.

host, path, insecure, apiKey, customUserAgent and cacheTtl were internal
vals, so Java callers had to pass every preceding constructor parameter
to set one. Make them public vars, like origin and consents and like the
iOS SDK.

apiKey, customUserAgent and cacheTtl now apply from the next call.
host, path and insecure build the base URL and storage keys, so they
are read when OptableSDK is created; the KDoc and README say so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant